---
---
<!DOCTYPE html>
<html lang=en>

<head>
	<meta charset=utf-8>

	<link rel="stylesheet" type="text/css" href="{{ site.baseurl }}/common/css/stylesheet.css"/>
	<link rel="stylesheet" href="{{ site.baseurl }}/common/css/stylesheet-fonts.css" type="text/css" charset="utf-8">
	<link rel="icon" href="{{ site.baseurl }}/common/css/favicon.ico" type="image/x-icon">
	<link rel="shortcut icon" href="{{ site.baseurl }}/common/css/favicon.ico" type="image/x-icon">
	<title>Upgrading to and Verifying Magento Community Edition and Enterprise Edition&mdash;Part 2</title>

</head>

<body>
<a name="top"></a>
<img src="{{ site.baseurl }}/common/images/m1x/m1xheader.png" width="1024" alt="header" />

<h1>Upgrading to and Verifying Magento Community Edition and Enterprise Edition&mdash;Part 2</h1>
<p><a href="{{ site.m1xgithuburl }}guides/m1x/install/installing_upgrade_details.html" target="_blank">Edit this page on GitHub <img src="{{ site.baseurl }}/common/images/github_icon.png" height="15px"></a></p>

 
<div class="toc"> <h4 class="toc">Table of Contents</h4> 
<ul>
<li><a href="#overview">概述</a></li>
<li><a href="#upgrade-ee-versions">Upgrade Roadmaps</a></li>
<li><a href="#prereq-tasks">Getting Ready For Your Upgrade</a></li>
<!-- <li><a href="#upgrade-mcm">Upgrading to Magento CE 1.8 or EE 1.13 Using Magento Connect Manager</a><li> -->
<li><a href="#upgrade-manual">Upgrading the File System, Solr, and Database</a></li>
<li><a href="#upgrade-manual-post-upgrade-ee11300">Running the URL Redirect Script <em>EE 1.13.0.0 and 1.13.0.1 only</em></a></li>
<li><a href="#upgrade-manual-run">Completing the Magento Upgrade</a></li>
<li><a href="#upgrade-manual-test">Testing the Magento Upgrade</a></li>
<li><a href="#install-privs-after">Setting Magento File System Permissions and Ownership After Upgrade</a></li>
<li><a href="#upgrade-troubleshoot">故障排除</a></li>
</ul></div>

<h2 id="overview">概述</h2>
<p>This article discusses how you upgrade to:</p>
<ul><li>Magento Community Edition (CE) 1.8 or 1.9.x</li>
<li>Magento Enterprise Edition (EE) 1.13.0.2, 1.13.1, or 1.14.x</li></ul>
<div class="msg-box important"><img src="{{ site.baseurl }}/common/images/m1x/icon-important.png" alt="important" align="left" width="40"><span><strong>Important</strong>: Magento recommends CE 1.9.1.0或更新 or EE 1.14.1.0或更新 for <em>all CE and EE installations and upgrades</em> to get the latest fixes, features, and security updates.</span></div>

<p>Because of changes to URL rewrites, the following upgrades are more complex than other upgrades.</p>
<ul><li>Upgrading from EE 1.12 or earlier to EE 1.14.x</li>
<li>Upgrading from EE 1.13.0.0 or EE 1.13.0.1 to EE 1.14.x</li></ul>
<div class="msg-box important"><img src="{{ site.baseurl }}/common/images/m1x/icon-note.png" alt="note" align="left" width="40"><span><strong>注意</strong>: If you're upgrading from EE 1.13.0.2 to EE 1.13.1.0或更新, your upgrade doesn't involve changes to URL rewrites and you can skip many of the steps discussed in the other upgrades. Continue with <a href="#prereq-tasks">Getting Ready For Your Upgrade</a>.</div>


<h2 id="upgrade-ee-versions">Upgrade Roadmaps</h2>
<ul><li>High-level roadmaps for upgrading to EE 1.13.0.2或更新 are discussed in <a href="{{ site.m1xgdeurl }}install/installing_upgrade_landing.html#ee1300-11301-upgrade-to-ee11302-start" target="_blank">Understanding the Upgrade to EE 1.13.0.2 or EE 1.14</a>.</li>
<li>To upgrade from EE 1.13.0.2 to EE 1.13.1.0或更新 (including EE 1.14.x), see <a href="#prereq-tasks">Getting Ready For Your Upgrade</a>.</li>
<li>To upgrade to CE 1.8 or 1.9, see <a href="{{ site.m1xgdeurl }}install/installing_upgrade_ce18_upgrade-roadmap.html" target="_blank">Upgrade Roadmap for CE 1.8 or 1.9</a></li></ul>

<h2 id="prereq-tasks">Getting Ready For Your Upgrade</h2>
<p>This section discusses how to get ready for your upgrade by backing up the database and customizations on the file system. The steps that follow do not affect your current production system. You can continue serving customers with no downtime.</p>
<p>To get ready for your upgrade:</p>
<ol><li>Get the Magento installation archive as discussed in <a href="{{ site.m1xgdeurl }}install/installing.html#get" target="_blank">Getting Magento CE or EE</a>.</li>
<li>安装Magento in a different directory:
<ul><li><em>Recommended</em>. Set up a new system (that is, another host) on which to install Magento.<br />
The system should be identical to, if not better than, your current system. The new system must meet the <a href="{{ site.m1xgdeurl }}system-requirements.html" target="_blank">Magento系统要求</a>.</li>
<li>安装Magento in a new, empty root installation directory on the same server.</li>
<div class="msg-box important"><img src="{{ site.baseurl }}/common/images/m1x/icon-important.png" alt="important" align="left" width="40"><span><strong>Important</strong>: <em>Do not</em> upgrade Magento in the same directory on the same server because post-upgrade errors are likely to occur.</span></div></li></ul>
</li>
<li>Magento <em>strongly</em> recommends you observe the following guidelines when you set up the Magento database in your development environment:
<ul>
<li>Magento for the first time uses <a href="http://dev.mysql.com/doc/refman/5.0/en/triggers.html" target="_blank">MySQL database triggers</a> to improve database access during reindexing. Magento does not support any custom triggers in the Magento database because custom triggers can introduce incompatibilities with future Magento versions.</li>
<li>Familiarize yourself with <a href="http://dev.mysql.com/doc/mysql-reslimits-excerpt/5.1/en/stored-program-restrictions.html" target="_blank">these potential MySQL trigger limitations</a> before you continue.</li>
<li>If you use MySQL database replication, Magento <em>does not</em> support MySQL statement-based replication. Make sure you use only <a href="http://dev.mysql.com/doc/refman/5.1/en/replication-formats.html" target="_blank">row-based replication</a>.</li>
<li>Review the MySQL recommendations for <a href="http://dev.mysql.com/doc/refman/5.0/en/password-security-user.html" target="_blank">MySQL password security</a>.</li></ul>
</li>
<li>Complete the tasks discussed in the following sections in the order shown:
<ol><li style="list-style-type:lower-alpha"><a href="#prereq-tasks-prod">Pre-Upgrade Tasks For Your Production Environment</a></li>
<li style="list-style-type:lower-alpha"><a href="#prereq-tasks-dev">Pre-Upgrade Tasks For Your Development Environment</a></li></ol>
</li></ol>

<h3 id="prereq-tasks-prod">Pre-Upgrade Tasks For Your Production Environment</h3>
<p>Complete the tasks discussed in the following sections in the order shown:</p>
<ol><li><a href="#prereq-tasks-prod-logging">Enabling Exception Logging</a></li>
<li><a href="#prereq-tasks-prod-disable-cron-11302">Disabling cron jobs <em>(EE 1.13.0.2或更新)</em></a></li>
<li><a href="#prereq-tasks-prod-index">Setting All Indexers for Update on Save</a></li>
<li><a href="#prereq-tasks-prod-clear-cache">Flushing the Cache</a></li>
<li><a href="#prereq-tasks-prod-backup-db">Backing Up the Database</a></li>
<li><a href="#prereq-tasks-prod-archive">Archiving Customizations and Extensions</a></li>
<li><a href="#prereq-tasks-prod-restore-settings">Restoring Configuration Settings</a></li>
</ol>

<h4 id="prereq-tasks-prod-logging">Enabling Exception Logging</h4>
<p>Before you start your upgrade, you should enable exception logging so it will be enabled on the development system. Without exception logging, it will be more difficult to diagnose errors during your upgrade. You can disable exception logging after you've exported the Magento database.</p>
<p>To enable exception logging:</p>
<ol><li>Log in to the Admin Panel as an administrator.</li>
<li>Click <strong>System</strong> > <strong>Configuration</strong>.</li>
<li>In the ADVANCED group, click <strong>Developer</strong>.<br />
This enables you to enable exception logging so you'll see exceptions in the development environment after the upgrade.</li>
<li>In the right pane, click <strong>Log Settings</strong> to expand it.<br />
The following figure shows an example.<br />
<img src="{{ site.baseurl }}/common/images/m1x/upgrade_log.png" height="338px" width="600px"></li>
<li>From the <strong>Enabled</strong> list, click <strong>Yes</strong>.</li>
<li>Optionally change the names of the log files.</li>
<li>Click <strong>Save Config</strong>.</li></ol>

<h4 id="prereq-tasks-prod-disable-cron-11302">Disabling cron Jobs</h4>
<p>Before upgrading to EE 1.13.0.2或更新, disable all running cron jobs. A simple way to stop cron jobs follows; consult an appropriate reference for other options.</p>
<p>As a user with <code>root</code> privileges, enter one of the following commands:</p>
<ul><li>Ubuntu: <code>service crond stop</code></li>
<li>CentOS: <code>service cron stop</code></li></ul>

<!-- <h4 id="prereq-tasks-prod-index111302">Setting All Indexers for Manual Update <em> (EE 1.13.0.2 only)</em></h4>
<p><em>This section applies to Magento EE 1.13.0.2 only</em>. Skip this section if you're using Magento CE.</p>
<p>Because of the changes to indexing in Magento EE 1.13, you must set all indexers to update on save before you upgrade; otherwise, unpredictable performance will result. You can revert indexer settings after you've exported the Magento database.</p>
<p>To set indexers to update on save:</p>
<ol><li>Click <strong>System</strong> > <strong>Index Management</strong>.</li>
<li>On the top left corner of the row, click <strong>Select All</strong> to select all indexers.</li>
<li>From the <strong>Options</strong> list, click <strong>Change indexing mode</strong>.<br />
The <strong>Index Mode</strong> list displays.</li>
<li>From the <strong>Index Mode</strong> list, click <strong>Manual Update</strong>.<br />
The following figure shows an example.<br />
<img src="{{ site.baseurl }}/common/images/m1x/upgrade_index-management_manual-update2.png" height="156px" width="600px"></li>
<li>At the top right corner, click <strong>Submit</strong>.</li>
<li>Make sure all indexers are now set for Manual Update as the following figure shows.<br />
<img src="{{ site.baseurl }}/common/images/m1x/upgrade_index-management_manual-update.png" height="156px" width="600px"></li></ol> -->

<h4 id="prereq-tasks-prod-index">Setting All Indexers for Update on Save<!--  <em>(EE 1.13.0.0 or 1.13.0.1 only)</em> --></h4>
<p><em>This section applies to upgrading Magento EE only</em>. Skip this section if you're using Magento CE.</p>
<p>Because of the changes to indexing in Magento EE 1.13, you must set all indexers to update on save before you upgrade; otherwise, unpredictable performance will result. You can revert indexer settings after you've exported the Magento database.</p>
<p>To set indexers to update on save:</p>
<ol><li>Click <strong>System</strong> > <strong>Index Management</strong>.</li>
<li>On the top left corner of the row, click <strong>Select All</strong> to select all indexers.</li>
<li>From the <strong>Options</strong> list, click <strong>Change indexing mode</strong>.<br />
The <strong>Index Mode</strong> list displays.</li>
<li>From the <strong>Index Mode</strong> list, click <strong>Update on Save</strong>.<br />
The following figure shows an example.<br />
<img src="{{ site.baseurl }}/common/images/m1x/upgrade_index-management.png" height="156px" width="600px"></li>
<li>At the top right corner, click <strong>Submit</strong>.</li>
<li>Make sure all indexers are now set for Update on Save as the following figure shows.<br />
<img src="{{ site.baseurl }}/common/images/m1x/upgrade_index-management2.png" height="156px" width="600px"></li></ol>

<h4 id="prereq-tasks-prod-clear-cache">Flushing the Cache</h4>
<p>Clear the Magento cache as follows:</p>
<ol><li>Log in to the Admin Panel as an administrator.</li>
<li>Click <strong>System</strong> > <strong>Cache Management</strong>.</li>
<li>Click <strong>Flush Magento Cache</strong>.</li></ol>

<h4 id="prereq-tasks-prod-backup-db">Backing Up the Database</h4>
<p>Back up your database using <code>mysqldump</code> or another tool. <code>mysqldump</code> syntax follows:</p>
<pre>mysqldump -u root <em>magento-database-name</em> > <em>export-file-name</em>.sql</pre>

<h4 id="prereq-tasks-prod-archive">Archiving Customizations and Extensions</h4>
<p>To archive your custom themes and extensions:</p>
<ol><li>Archive the Magento <code>media</code> directory and all subdirectories. 例如，<br />
<pre>cd [your Magento install dir]
tar -czf media.tgz media</pre></li>
<li>Archive any custom themes in the following directories:<br />
<pre>[your Magento install dir]/app/design/frontend
[your Magento install dir]/skin/frontend</pre></li>
<li>Archive any customizations or extensions in the following directories:<br />
<pre>[your Magento install dir]/app/code/local
[your Magento install dir]/app/code/community</pre></li>
<li>Transfer the archives you just created to the development environment.</li>
<li>Copy <code>[your Magento install dir]/app/etc/local.xml</code> to your development environment.</li>
</ol>

<h4 id="prereq-tasks-prod-restore-settings">Restoring Configuration Settings</h4>
<p>After you've exported the Magento database and extensions, you can revert the configuration changes you made as discussed in these sections:</p>
<ul><li><a href="#prereq-tasks-prod-logging">Enabling Exception Logging</a></li>
<li><a href="#prereq-tasks-prod-index">Setting All Indexers for Update on Save <em>(EE only)</em></a></li></ul>

<h3 id="prereq-tasks-dev">Pre-Upgrade Tasks For Your Development Environment</h3>
<p>In your development environment:</p>
<ol><li>If necessary, create a Magento installation master directory; Magento installs in a <code>magento</code> subdirectory of that directory.<br />
The Magento installation archive creates a <code>magento</code> subdirectory so if you want your Magento installation directory to be <code>/var/www/magento</code>, you don't need to do anything.<br />
<div class="msg-box important"><img src="{{ site.baseurl }}/common/images/m1x/icon-tip.png" alt="tip" align="left" width="40"><span><strong>Tip</strong>: The name and path to the Magento installation directory in your development system does not have to be the same as on your production system, although it might make some tasks simpler.</span></div>

<li>Create a new database instance. 例如， you can create a new MySQL database instance named <code>magento</code> using the following commands:<br />
<pre>mysql -u root -p</pre>
Enter the remaining commands at the <code>mysql></code> prompt
<pre>create database magento;
GRANT USAGE ON *.* TO magento@localhost IDENTIFIED BY 'magento';
GRANT ALL ON magento.* TO magento@localhost;</pre>
For MySQL versions later than 5.0.2 but earlier than 5.1.6, the following command is required:
<pre>GRANT SUPER ON *.* TO 'magento'@'localhost';</pre>
Exit the MySQL command shell:
<pre>exit</pre>
Verify the database exists using the following command:
<pre>mysql -u magento -p magento</pre>
If an error displays, repeat the commands. If the command succeeded, enter <code>exit</code> to return to the command prompt.</li>
<li>If you're using <a href="http://selinuxproject.org/page/Main_Page" target="_blank">Linux增强安全(SELinux)</a> <em>and</em> Apache must initiate a connection to another host, you must run the commands discussed in this step.
<ol><li style="list-style-type:lower-alpha">To determine if SELinux is enabled, use the following command:
<code>getenforce</code><br />
<code>Enforcing</code> displays to confirm that SELinux is running.</li>
<li style="list-style-type:lower-alpha">Enter one of the following commands:<br />
CentOS:
<pre>setsebool -P httpd_can_network_connect=1</pre>
Ubuntu
<pre>setsebool -P apache2_can_network_connect=1</pre></li></ol>
</li></ol>

<h4 id="prereq-tasks-dev-php">Optional: Upgrading to PHP 5.4</h4>
<p>PHP 5.3 is currently the latest PHP version available in the default repositories for Ubuntu and CentOS. PHP 5.3 works with CE 1.8, CE 1.9, EE 1.13, and EE 1.14.</p>
<p>We recommend PHP 5.4 for all of the preceding CE and EE versions because of the <a href="http://php.net/ChangeLog-5.php#5.4.0" target="_blank">new features and changes</a> in that release.</p>
<p>CE 1.8 and EE 1.13 both require a <a href="{{ site.m1xgdeurl }}other/php5.4_patch.html" target="_blank">PHP 5.4 patch</a>. The patch is listed as <strong>PHP 5.4 Compatibility</strong> in the EE support portal.</p>

<h5>Upgrading to PHP 5.4&mdash;Ubuntu</h5>
<p>Use the instructions on <a href="http://phpave.com/upgrade-php-5-3-php-5-5-ubuntu-12-04-lts/" target="_blank">phpave</a>.</p>

<h5>Upgrading to PHP 5.4&mdash;CentOS</h5>
<p>Enter the following commands in the order shown as a user with <code>root</code> privileges:</p>
<pre>cd /tmp
rpm -Uvh http://download.fedoraproject.org/pub/epel/6/i386/epel-release-6-8.noarch.rpm
rpm -Uvh http://rpms.famillecollet.com/enterprise/remi-release-6.rpm
yum --enablerepo=remi install httpd php php-common</pre>
<p>The following resources are also available:</p>
<ul><li><a href="http://kb.parallels.com/en/115875" target="_blank">kb.parallels</li>
<li><a href="http://stackoverflow.com/questions/21502656/upgrading-php-on-centos-6-5-final" target="_blank">stackoverflow</a></li>
<li><a href="http://rpms.famillecollet.com/" target="_blank">remi repository</a></li></ul>

<h2 id="upgrade-manual">Upgrading the File System, Solr, and Database</h2>
<p>Upgrade your Magento installation by completing all of the following tasks in the order shown:</p>
<ol><li><a href="#upgrade-manual-prereq">Upgrade Requirements</a></li>
<li><a href="#upgrade-manual-file-sys">Upgrading Assets on the Magento File System</a></li>
<li><a href="#upgrade-manual-db">Upgrading the Magento Database</a></li>
<li><a href="#upgrade-manual-solr">Upgrading Solr (<em>EE 1.14.0.0 only</em>)</a></li>
<li><a href="#upgrade-manual-cleanup">Finishing the File System</a></li></ol>

<h3 id="upgrade-manual-prereq">Upgrade Requirements</h3>
<p>Before attempting your Magento upgrade, complete all the tasks discussed in:</p>
<ul><li><a href="#prereq-tasks">Getting Ready for Your Upgrade</a></li>
<li><a href="{{ site.m1xgdeurl }}install/installing.html#get">Getting Magento CE or EE</a></li></ul>

<h3 id="upgrade-manual-file-sys">Upgrading Assets on the Magento File System</h3>
<p>This section discusses how to extract the Magento archive in your development system and manually copy over your customizations, themes, and extensions.</p>
<div class="msg-box important"><img src="{{ site.baseurl }}/common/images/m1x/icon-important.png" alt="important" align="left" width="40"><span><strong>Important</strong>: To avoid errors after upgrading, you <em>must</em> set up a parallel system. <em>Do not</em> upgrade your existing system or post-upgrade errors are likely to occur.</span></div>

<ol><li>Make sure the CE or EE installation archive is located in the directory above where you want Magento to be installed.<br />
例如， to install Magento to <code>/var/www/magento</code>, copy the archive to <code>/var/www</code>.</li>
<li>Extract the archive. 例如，
<code>tar -zxf <em>archive-name</em></code><br />
This installs Magento CE or EE on the file system on your development system. Next, you'll overwrite some of these assets with customizations from your production system.</li>
<li>Extract the production system's <code>media</code> archive, overwriting the installation archive. You created the <code>media</code> archive as discussed in <a href="#prereq-tasks">Getting Ready For Your Upgrade</a>.<br />
<div class="msg-box important"><img src="{{ site.baseurl }}/common/images/m1x/icon-tip.png" alt="tip" align="left" width="40"><span><strong>Tip</strong>: Copy the media archive to the same level in the directory structure to simplify the process. 例如， if you created the media archive on your production system in your Magento install directory, the archive when extracted creates the <code>media</code> directory and all subdirectories. If you copy the media archive to the Magento installation directory on your development system, extracting it automatically replaces existing <code>media</code> subdirectory contents.</span></div></li>
<li>If necessary, move the <code>media</code> directory and subdirectories to <code>media</code> directory in your new Magento installation, overwriting the existing contents.</li>
<li>Extract the custom theme package archive you created as discussed in <a href="#prereq-tasks">Getting Ready For Your Upgrade</a>.</li>
<li>If necessary, move the theme packages to the <code>[your Magento install dir]/app/design/frontend</code>和<code>[your Magento install dir]/skin/frontend</code> directories, as appropriate, overwriting the existing contents.</li>
<li>Extract the customization and extension archives you created as discussed in <a href="#prereq-tasks">Getting Ready For Your Upgrade</a>.</li>
<li>If necessary, move the extensions and customizations to the <code>[your Magento install dir]/app/code/local</code>和<code>[your Magento install dir]/app/code/community</code> directories, as appropriate, overwriting the existing contents.</li></ol>

<h3 id="upgrade-manual-db">Updating the Magento Database</h3>
<p>This section discusses how to:</p>
<ul><li>Import the production database data into the development database instance.</li>
<li>In the development database instance, change the values of the paths <code>web/unsecure/base_url</code>和<code>web/secure/base_url</code> in the <code>core_config_data</code> table to the development server's IP address or host name.</li></ul>
<p>Import the production database data using your database manager tool.</p>
<div class="msg-box important"><img src="{{ site.baseurl }}/common/images/m1x/icon-important.png" alt="important" align="left" width="40"><span><strong>Important</strong>:The database instance into which you import <em>must be empty</em>.</span></div>

<p><code>mysql</code> syntax follows:</p>
<pre>mysql -u root -p <em>database-name</em> &lt; <em>database-export-filename</em>.sql</pre>
例如， if the database name is <code>magento</code> and the database export file name is <code>mangento-db-export.sql</code>, enter
<pre>mysql -u root -p magento &lt; mangento-db-export.sql</pre></li>
<p>The following sections discuss how to change the base URL paths from <code>http://prod.example.com</code> to <code>http://dev.example.com</code> using SQL commands and phpmyadmin:</p>
<ul><li><a href="#upgrade-manual-db-sql">Updating the Base URL the Database Using SQL Commands</a></li>
<li><a href="#upgrade-manual-db-phpmyadmin">Updating the Base URL the Database Using phpmyadmin</a></li></ul>

<h4 id="upgrade-manual-db-sql">Updating the Base URL the Database Using SQL Commands</h4>
<p>This section discusses how to update the secure and unsecure URLs of your webstores and store views in the Magento database. The following example assumes you have two URLs, which every Magento installation has by default. Depending on your setup, you could have more (for additional store views, 内容分发网络s (CDNs) and so on.</p>
<p>Use the following procedure to update <em>all</em> matching URLs in the database.</p>
<p>To update the database with the development system's base URLs using SQL commands:</p>
<ol><li>Log in to the database server as any user.</li>
<li>Enter the following commands in the order shown:
<pre>mysql -u root -p</pre>
Enter the remaining commands at the mysql> prompt.
<pre>use <em>magento-db-name</em>;
SELECT * FROM core_config_data WHERE path LIKE '%base_url%';</pre></li>
<li>In the resulting output, make note of the rows that include <code>web/unsecure/base_url</code>和<code>web/secure/base_url</code>.<br />
In particular, you must know the value of the <code>config_id</code> for these rows.</li>
<li>Carefully examine the <em>entire URL</em> to avoid mistakes.</li>
<li>Enter the following command to update the values of <code>web/unsecure/base_url</code>和<code>web/secure/base_url</code>:
<pre>UPDATE core_config_data SET value='<em>base-url</em>' WHERE config_id=<em>id1</em> or config_id=<em>id2</em>;</pre>
Example 1&mdash;<code>config_ids</code> are the same: if your base URL is <code>http://dev.example.com/</code>, the <code>config_id</code> of the row containing <code>web/unsecure/base_url</code> is 354 and the <code>config_id</code> of the row containing <code>web/secure/base_url</code> is 355, enter:
<pre>UPDATE core_config_data SET value='http://dev.example.com/' WHERE config_id=354 or config_id=355;</pre>
Example 2&mdash;<code>config_ids</code> are different: Same as preceding example except that <code>web/secure/base_url</code> uses <code>https://</code>
<pre>UPDATE core_config_data SET value='http://dev.example.com/' WHERE config_id=354;
UPDATE core_config_data SET value='https://dev.example.com/' WHERE config_id=355;</pre></li>
<li>Verify the values are set correctly.
<pre>SELECT * FROM core_config_data WHERE path LIKE '%base_url%';</pre></li>
<li>For other URLs, be careful to perform the replacement correctly.<br />
例如， store view base link URLs resemble the following:<br />
<pre>http://prod.example.com/view1/</pre>
Make sure to update the URL like the following:
<pre>UPDATE core_config_data SET value='http://dev.example.com/view1/' WHERE config_id=377;</pre></li>
<li>When you're done, run the following command again:<br />
<pre>SELECT * FROM core_config_data WHERE path LIKE '%base_url%';</pre></li>
<li>If the values are set correctly, enter <code>exit</code> at the <code>mysql></code> prompt and continue with <a href="#upgrade-manual-cleanup">Finishing the File System</a>.<br />
If not, repeat the tasks discussed in this section. <em>Do not continue</em> until the database is updated.</li>
</ol>

<h4 id="upgrade-manual-db-phpmyadmin">Updating the Base URL the Database Using phpmyadmin</h4>
<p>This section discusses how to use phpmyadmin to change the values of the paths <code>web/unsecure/base_url</code>和<code>web/secure/base_url</code> in the <code>core_config_data</code> table to the development server's IP address or host name.</p>
<ol><li>In a web browser's location or address field, enter <code><em>dev-web-server-host-or-ip</em>/phpmyadmin</code>
例如， if your web server address is <code>http://dev.example.com</code>, enter
<code>http://dev.example.com/phpmyadmin</code></li>
<li>Log in as the MySQL <code>root</code> user.</li>
<li>In the left navigation bar, click the name of your Magento database.</li>
<li>In the left navigation bar, click the <strong>core_config_data</strong> table.</li>
<li>At the top of the page, click the <strong>Search</strong> tab.</li>
<li>In the Search tab page, from the <strong>Operator</strong> list, click <strong>LIKE</strong>.</li>
<li>Enter <code>%base_url%</code> in the <strong>Value</strong> field.<br />
The following figure shows an example.<br />
<img src="{{ site.baseurl }}/common/images/m1x/install_myphpadmin_search.png" height="279px" width="600px"></li>
<li>Click <strong>Go</strong>.<br />
The following figure shows sample results.<br />
<img src="{{ site.baseurl }}/common/images/m1x/install_myphpadmin_results.png" height="139px" width="600px"></li>
<li>Click <img src="{{ site.baseurl }}/common/images/m1x/install_myphpadmin_edit-icon.png"> (Edit) in the row that includes the path <code>web/unsecure/base_url</code>.</li>
<li>Change the value to the host name or IP address of your development server.<br />
The following figure shows an example.<br />
<img src="{{ site.baseurl }}/common/images/m1x/install_myphpadmin_edit.png" height="333px" width="600px">
<li>Click <strong>Go</strong>.</li>
<li>Repeat these tasks for the path that includes <code>web/secure/base_url</code>.</li>
<li>Exit phpmyadmin.</li></ol>
</li></ol> 

<h3 id="upgrade-manual-solr">Upgrading Solr (EE 1.14.0.0 only)</h3>
<p><em>This section applies to upgrading to EE 1.14.0.0 using the Solr search engine only</em>. If you're upgrading to a different version&mdash;or if you're not using Solr&mdash;skip this section and continue with <a href="#upgrade-manual-cleanup">Finishing the File System</a>.</p>
<p>Because of changes to the Solr schema, you must copy two files from Magento to your Solr installation. Failure to do so might prevent products from displaying on your web store. After copying the files, you must also reindex the catalog search index.</p>
<p>To update Solr:</p>
<ol><li>If the Solr search engine is running, stop it.</li>
<li>Copy the following files from the Magento 1.14.0.0 installation to the equivalent directory on your Solr installation:
<pre>[your Magento install dir]/lib/Apache/Solr/conf/schema.xml
[your Magento install dir]/lib/Apache/Solr/conf/solrconfig.xml</pre>
<p>例如， if Magento is installed in <code>/var/www/html/magento</code> and the example Solr configuration is installed in the <code>/etc/solr/apache-solr-3.6.2/example/solr/conf</code> directory on the same host, enter:</p>
<pre>cp /var/www/html/magento/lib/Apache/Solr/conf/solrconfig.xml /etc/solr/apache-solr-3.6.2/example/solr/conf
cp /var/www/html/magento/lib/Apache/Solr/conf/schema.xml /etc/solr/apache-solr-3.6.2/example/solr/conf</pre></li>
<li>Restart Solr.</li>
<li>After you copy the files, you must update the catalog search index. To update the catalog search index, open a command prompt window.</li>
<li>Change to the <code>shell</code> subdirectory of your Magento installation directory.<br />
例如， on CentOS:
<pre>cd /var/www/html/magento/shell</pre></li>
<li>输入下面的命令：
<pre>php indexer.php --reindex catalogsearch_fulltext</code></li></ol>
<div class="msg-box important"><img src="{{ site.baseurl }}/common/images/m1x/icon-note.png" alt="note" align="left" width="40"><span><strong>注意</strong>: The preceding example showed paths used by the Solr example configuration. Solr ships with a sample configuration that Magento suggests you use for development only. Do not use the Solr example configuration in production.</div>

<h3 id="upgrade-manual-cleanup">Finishing the File System</h3>
<p>This section discusses how to edit copy <code>local.xml</code> and set file system permissions and ownership on the production system.</p>

<h4 id="upgrade-manual-cleanup-localxml">Copying local.xml</h4>
<ol><li>Copy your production system's <code>local.xml</code> to <code>[your Magento install dir]/app/etc</code>.</li>
<li>Open <code>local.xml</code> in a text editor.</li>
<li>If necessary, change the database connection information in the <code>default_setup</code> element, as follows:
<pre>&lt;default_setup>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;connection>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;host>&lt;![CDATA[<em>change-if-necessary</em>]]>&lt;/host>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;username>&lt;![CDATA[<em>change-if-necessary</em>]]>&lt;/username>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;password>&lt;![CDATA[<em>change-if-necessary</em>]]>&lt;/password>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;dbname>&lt;![CDATA[<em>change-if-necessary</em>]]>&lt;/dbname>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;initStatements>&lt;![CDATA[SET NAMES utf8]]>&lt;/initStatements>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;model>&lt;![CDATA[mysql4]]>&lt;/model>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;type>&lt;![CDATA[pdo_mysql]]>&lt;/type>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;pdoType>&lt;![CDATA[]]>&lt;/pdoType>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;active>1&lt;/active>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;/connection>
&lt;/default_setup></pre></li>
<li>Save your changes to <code>local.xml</code> and exit the text editor.</li></ol>

<h4 id="upgrade-manual-cleanup-perms">Setting File and Directory Ownership and Privileges</h4>
<p>Magento recommends the following ownership and privilege settings for files and directories in the Magento installation directory:</p>
<ul><li>The Magento installation directory and all subdirectories are owned by the web server user.<br />
This enables the web server to change files in these subdirectories but other users cannot access them (except a higher-level user such as <code>root</code>).</li>
<li>All directories have 700 permissions (<code>drwx------</code>).<br />
700 permissions give full control (that is, read/write/execute) to the owner and no permissions to anyone else.</li>
<li>All files have 600 permissions (<code>-rw-------</code>).<br />
600 permissions mean the owner can read and write but other users have no permissions.</li></ul>
<p><strong>注意</strong>: The way you set permissions and ownership depends on whether Magento is running on a dedicated or hosted system:</p>
<ul><li><em>Hosted</em>: A Magento server located on a hosting provider. A <em>hosted</em> system typically does not enable you to elevate to <code>root</code>. The web server typically runs as an ordinary user. Magento assumes you log in as this user to start and stop the web server and that you already own all the files and directories in the Magento installation directory. You can use <code>chmod</code> to change permissions on files and directories.</li>
<li><em>Dedicated</em>: A Magento server you control and operate. Unlike a hosted system, you can elevate to <code>root</code> and, as <code>root</code>, you can use the <code>chown</code>和<code>chmod</code> commands to set ownership and privileges in the Magento installation directory.</li></ul>
<p>To set privileges and ownership:</p>
<ol><li>Log in to your Magento server.</li>
<li>Change to your Magento installation directory:
<pre>#Ubuntu example
cd /var/www/magento

#CentOS example
cd /var/www/html/magento</pre></li>
<li><em>Dedicated Magento server only</em>. Enter the following command to set ownership of the Magento installation directory and all its subdirectories:
<pre>chown -R <em>web-server-user-name</em> .</pre>
例如， on Ubuntu where Apache usually runs as <code>www-data</code>, enter
<pre>chown -R www-data .</pre></li>
<li>Enter the following commands to set directory permissions to 700 and file permissions to 600:
<pre>find . -type d -exec chmod 700 {} \;
find . -type f -exec chmod 600 {} \;</pre></li></ol>

<!-- Start by changing to your Magento installation directory:
<code>#Ubuntu example<br />
cd /var/www/magento<br />
<br />
#CentOS example<br />
cd /var/www/html/magento</code></li>
<li>Set file permissions.
<code>find . -type f -exec chmod 644 {} \;</code></li>
<li>Set directory permissions.
<code>find . -type d -exec chmod 755 {} \;</code></li>
<li>Make the <code>var</code>, <code>app/etc</code>,以及<code>media</code> directories and subdirectories world-writable.
<code>chmod -R 777 media app/etc var var/.htaccess</code></li>
<li>Change to the directory above the Magento install directory.
<code>#Ubuntu example<br />
cd /var/www<br />
<br />
#CentOS example<br />
cd /var/www/html</code></li>
<li>Set ownership.
<code>#If you're not sure, find the web server group<br />
ps -o "user group command" -C httpd,apache2<br />
<br />
#Set ownership<br />
chown -R <em>your-user-name</em>:<em>web-server-group</em> magento<br />
<br />
#Ubuntu example<br />
chown -R myuser:www-data magento</code></li></ol> -->

<h2 id="upgrade-manual-post-upgrade-ee11300">Running the URL Redirect Script (EE 1.13.0.0 and 1.13.0.1 only)</h2>
<p>If you're upgrading to EE 1.14 from EE 1.13.0.0 or 1.13.0.1, see <a href="{{ site.m1xgdeurl }}install/installing_upgrade_from-ee11300-or-01.html" target="_blank">EE 1.13.1.0 Upgrade: Running the EE 1.13.0.0 or EE 1.13.0.1 URL Redirect Script</a> now. When you're done, return here to continue your upgrade.</p>

<h2 id="upgrade-manual-run">Completing the Magento Upgrade</h2>
<p>To complete the upgrade, go to your Magento base URL in a web browser. The first time you go to your Magento base URL, server-side scripts run to update the database. Depending on the amount of data in your database, this process can take a long time.</p>
<div class="msg-box important"><img src="{{ site.baseurl }}/common/images/m1x/icon-important.png" alt="important" align="left" width="40"><span><strong>Important</strong>: <em>Completing the upgrade requires downtime on your production system</em>. If you continue to take orders on your production system, there is no way to reconcile all of the new orders in the replacement development system. You can reduce the amount of downtime to a minimum by thoroughly testing your development system before shutting down production.</span></div>


<p>If you're upgrading from a version earlier than CE 1.4 or EE 1.7, Magento <em>strongly recommends</em> the two-step upgrade approach discussed in <a href="{{ site.m1xgdeurl }}install/installing_upgrade_landing.html#upgrade-path">Upgrade Path</a>. In addition, you should expect the upgrade and testing process to take a long time and to expect more downtime for your production system.</p></p>
<p>Complete the following tasks in the order shown:</p>
<ol><li><a href="#upgrade-manual-scripts">Running the Upgrade Scripts and Fixing Exceptions</a></li>
<li><a href="#upgrade-manual-post-upgrade-11302">Running the URL Redirect Script <em>(EE 1.12.x and earlier only)</em></a></li>
<li><a href="#upgrade-manual-post-upgrade-11300">Post-Upgrade Tasks <em>(EE 1.13.0.1 Only)</em></a></li> 
<li>To apply the <a href="https://magento.com/security/patches/supee-8788" target="_blank">security patch</a> released in October, 2016, see <a href="http://devdocs.magento.com/guides/m1x/other/ht_install-patches.html#apply-8788" target="_blank">How to Apply the SUPEE-8788 Patch</a>.</li>
<li><a href="#upgrade-manual-cron">Setting Up the Magento Cron Job</a></li>
<li><a href="#upgrade-manual-var">Clearing Magento var/ Subdirectories</a></li>
<li><a href="#upgrade-manual-index">Verifying the Status of Indexers</a></li>
<li><a href="#upgrade-manual-test">Testing the Magento Upgrade</a></li>
<li><a href="#upgrade-downtime">Taking Your Old Production System Offline</a></li></ol>

<h3 id="upgrade-manual-scripts">Running the Upgrade Scripts and Fixing Exceptions</h3>
<p>The first step in your upgrade is to run server-side upgrade scripts. Depending on the nature of your customizations and extensions, and how many customers and products are in your database, these scripts can take a long time to run and can result in exceptions. You must resolve all exceptions before continuing to the next step in the process.</p>
<p>This step in the upgrade process is iterative; that is, you'll probably run through it more than once.</p>
<div class="msg-box important"><img src="{{ site.baseurl }}/common/images/m1x/icon-note.png" alt="note" align="left" width="40"><span><strong>注意</strong>: Your production system remains up during this step in the upgrade process. You can continue taking and shipping orders and also making changes in the Admin Panel.</div>
<p>To run the upgrade scripts:</p>
<ol><li>In a web browser address or location field, enter your Magento installation's base URL.<br />
<div class="msg-box important"><img src="{{ site.baseurl }}/common/images/m1x/icon-note.png" alt="note" align="left" width="40"><span><strong>注意</strong>: If you upgraded Magento on the same server, you might need to update your Apache web server's virtual host configuration to reference the new Magento installation directory. For more information about configuring virtual hosts, see the <a href="http://httpd.apache.org/docs/2.2/vhosts" target="_blank">Apache Virtual Host documentation</a>.</div>

(You updated the Magento database with the development system base URL as discussed in <a href="#upgrade-manual-db">Updating the Magento Database</a>.)</li>
<li>Wait while upgrade scripts run on the server.</li>
<li>If fatal errors or exceptions display in the browser, they are most likely related to customizations. To resolve fatal errors, you must:
<ol><li style="list-style-type:lower-alpha">Analyze the errors to determine the root cause.<br />
You can find errors in the web server's error log or in <code>[your Magento install dir]/var/log</code>.</li>
<li style="list-style-type:lower-alpha">Fix the cause in your extension code.</li>
<li style="list-style-type:lower-alpha">In your development environment, drop the Magento database.</li>
<li style="list-style-type:lower-alpha">Re-create the development database and import production data into it as discussed in <A href="#upgrade-manual-db">Updating the Magento Database</a>.</li>
<li style="list-style-type:lower-alpha">Use the following command to delete the contents of the Magento <code>var/</code> subdirectories:
<pre>rm -rf [your Magento install dir]/var/cache [your Magento install dir]/var/full_page_cache \
	[your Magento install dir]/var/locks [your Magento install dir]/var/session</pre>
<div class="msg-box important"><img src="{{ site.baseurl }}/common/images/m1x/icon-note.png" alt="note" align="left" width="40"><span><strong>注意</strong>: Some of these directories might be empty; this is normal.</div></li>
<li style="list-style-type:lower-alpha">Clean up the file system as discussed in <a href="#upgrade-manual-cleanup">Finishing the File System</a>.</li>
<li style="list-style-type:lower-alpha">Repeat step 1 in this section.</li>
<li style="list-style-type:lower-alpha">Repeat the tasks discussed in this section until no more fatal errors display in the browser.</li></ol>
</li></ol>

<h3 id="upgrade-manual-post-upgrade-11300">Post-Upgrade Tasks (EE 1.13.0.1 Only)</h3>
<p><em>This section applies to upgrading from 1.13.0.1 only.</em> If you're upgrading CE or if you're upgrading from a different EE version, continue with <a href="#upgrade-manual-cron">Setting Up the Magento Cron Job</a>.</p>
<p>After successfully running the Magento upgrade and fixing errors, enter the following command from the Magento root directory:</p>
<pre>php -f shell/indexer.php -- --reindexall</pre>
<p>This command runs a full reindex and it might take a long time, depending on the size of your database.</p>
<p>After the reindex completes, enter the following command from your Magento installation directory:</p>
<pre>rm -rf var/cache var/full_page_cache var/locks</pre>
<p>Continue with <a href="#upgrade-manual-cron">Setting Up Magento Cron Jobs</a>.</p>

<h3 id="upgrade-manual-post-upgrade-11302">Running the URL Redirect Script (EE 1.12.x and Earlier Only)</h3>
<p>If you're upgrading to EE 1.14 from EE 1.12 or earlier, see <a href="{{ site.m1xgdeurl }}install/installing_upgrade_from-ee112.html" target="_blank">EE 1.14 Upgrade: Running the EE 1.12 and Earlier URL Redirect Script</a> now. When you're done, return here to continue your upgrade.</p>
<!-- <h3 id="upgrade-manual-post-upgrade-ee112">Running a Full Reindex <em>(EE 1.13.0.0 or 1.13.0.1 only)</em></h3>
<p>If you're upgrading from EE 1.13.0.0 or 1.13.0.1, enter the following commands as a user with <codE>root</code> privileges to fully reindex:</p>
<ol><li>Change to the Magento installation directory.</li>
<li>输入下面的命令：<br />
<code>php -f shell/indexer.php -- --reindexall</code></li>
<li>Wait while Magento reindexes; if you have a large database, reindexing can take a long time.</li>
<li>Clear the Magento <code>var/</code> subdirectories as discussed in the next section.</li></ol> -->

<h3 id="upgrade-manual-cron">Setting Up the Magento Cron Job</h3>
<p>You should now set up your Magento cron job as discussed <a href="{{ site.m1xgdeurl }}install/installing_install.html#install-cron" target=_"blank">here</a>.</p>

<h3 id="upgrade-manual-var">Clearing Magento var/ Subdirectories</h3>
<p>Run the following command to clean the Magento <code>var/</code> subdirectories:</p>
<pre>rm -rf [your Magento install dir]/var/cache [your Magento install dir]/var/full_page_cache [your Magento install dir]/var/locks</pre>
<div class="msg-box important"><img src="{{ site.baseurl }}/common/images/m1x/icon-note.png" alt="note" align="left" width="40"><span><strong>注意</strong>: Some of these directories might be empty; this is normal.</div>

<h3 id="upgrade-manual-index">Verifying the Status of Indexers</h3>
<p>After the cron job runs, all indexers should be in a Ready status. Before testing your upgrade, verify all indexers are Ready; otherwise, your testing will be inconclusive.</p>
<p>To verify the status of indexers:</p>
<ol><li>Log in to the Admin Panel as an administrator.</li> 
<li>Click <strong>System</strong> > <strong>Index Management</strong>.<br />
Verify that all indexers have a status of Ready, as the following figure shows.<br />
<img src="{{ site.baseurl }}/common/images/m1x/upgrade_index-management_after.png" width="600px" height="154px"/></li>
<li>If indexers are <em>not</em> Ready, use the following guidelines:
<table>
<tbody>
<tr>
  <th>Indexer status</th>
  <th>Suggested action</th>
</tr>
<tr>
  <td>Scheduled</td>
  <td>Wait for cron to finish or run <code>http://<em>magento-host-name</em>/cron.php</code> from a web browser.</td>
</tr>
<tr>
  <td>Processing</td>
  <td><p>Wait for cron to finish or run <code>cron.php</code> from a web browser. (例如， <code>http://www.example.com/magento/cron.php</code>)</p>
  <p>If indexers are Processing for an extended period of time, run the command discussed in <a href="#upgrade-manual-var">Clearing Magento var/ Subdirectories</a> and refresh the Index Management page.</p></td>
</tbody>
</table></li></ol>

<h3 id="upgrade-manual-test">Testing the Magento Upgrade</h3>
<p>After you have upgraded with no fatal errors or exceptions, Magento strongly recommends you thoroughly test the upgrade in your development environment as follows:</p>
<ol><li>Test all extensions and customizations thoroughly.<br />
Make sure the UIs perform as expected, make sure the extensions behave properly, and so on.</li>
<li>Run some orders, making sure prices are calculated correctly and that orders go through the configured payment mechanisms.</li>
<li>If you encounter issues, <a href="{{ site.m1xgdeurl }}install/installing.html#help" target="_blank">get help</a>.</li>
<li>Before making the development system live, back up everything in your production and development environments again.<br />
The way you make your development system live is up to you; a simple way is to update your DNS server to point to the development IP address.</li></ol>

<h3 id="upgrade-downtime">Taking Your Old Production System Offline</h3>
<p>The last step in upgrading is to take your production system offline and switching to your development system&mdash;which then becomes the production system from that point on.</p>
<div class="msg-box important"><img src="{{ site.baseurl }}/common/images/m1x/icon-important.png" alt="important" align="left" width="40"><span><strong>Important</strong>: Before continuing, make sure all errors have been resolved and that you have thoroughly tested the upgrade as discussed in the preceding section.</span></div>
<p>To switch from your production to development system:</p>
<ol><li>Put your production system in maintenance mode so it cannot accept orders or other changes.<br />
To do so, create an empty file named <code>[your Magento install dir]/maintenance.flag</code>.</li>
<li>Test it by going to your Magento web store's front page.<br />
The following message displays if you set up maintenance mode correctly:
<code>The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.</code></li>
<li>If necessary, update the development database again to get any final transactions processed by your current production system.<br />
For details, see <a href="#upgrade-manual-db">Updating the Magento Database</a>.</li>
<li>Put your production system in maintenance mode so it cannot process orders.</li>
<li>Make your development system live.<br />
The way you do this is up to you; typically, you can configure your DNS server to send requests for your web store domain to the development system's IP address. Be aware that propagating the change to other DNS servers can take some time.</li>
<li>Verify your former development system is functioning as your new Magento web store in production.</li>
<li>Shut down the old production system.</li></ol>
<p>Congratulations! You successfully upgraded! Review our <a href="{{ site.m1xgdeurl }}ce19-ee114-home.html">welcome page</a> to see the improvements you're getting.</p>

<h2 id="install-privs-after">Setting Magento File System Permissions and Ownership After Upgrade</h2>
<p>To secure your Magento installation after the upgrade, see <a href="{{ site.m1xgdeurl }}install/installer-privileges_after.html" target="_blank">After You 安装Magento: Recommended File System Ownership and Privileges</a>.</p>

<h2 id="upgrade-troubleshoot">故障排除</h2>
<p>There is a known issue after upgrading to EE 1.13.1 that affects you <em>only</em> if you do <em>not</em> follow the recommended procedure to upgrade to a new environment as discussed in <a href="#prereq-tasks">Getting Ready For Your Upgrade</a>.</p>
<p><strong>Symptom</strong>: After completing the upgrade, when you log in to the Admin Panel and click <strong>System</strong> > <strong>Configuration</strong>, a fatal error similar to the following displays in your browser:</p>
<pre>Class 'Mage_Googlecheckout_Helper_Data' not found in /var/www/html/magento/app/Mage.php on line 547</pre>
<!-- <p><strong>描述</strong>: TBD -->
<p><strong>Solution</strong>:</p>
<ol><li>Close the Admin Panel browser window.</li>
<li>As a user with <code>root</code> privileges, delete all files <em>except</em> <code>config.xml</code> from the following directory:<br />
<pre>[your Magento install dir]/app/code/core/Mage/GoogleCheckout/etc</pre></li>
<li>When you log back in to the Admin Panel, everything works as expected.</li></ol>

<p>In the event of any other issue during the upgrade, see <a href="{{ site.m1xgdeurl }}install/installing.html#help" target="_blank">Getting Help With Your Installation or Upgrade</a>.</p>
 
</p>
